-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OOC-3753 - Merge remote-tracking branch 'upstream/main' into test-branch #198
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did we have a plan for what to do with the main branch? Is it worth the main branch just being a mirror of the upstream maybe?
@@ -1623,33 +1623,6 @@ | |||
} | |||
] | |||
}, | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Were these ones just not used anymore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, they were defined but not used anywhere so I removed them to tidy the form up a bit
Have you tried deploying the branch to dev? Just curious if lots of dependency upgrades might break the deployment pipeline in some way |
Not yet but that's a good shout, I'll try deploying to dev now and let's see what happens |
This brings our repo back in line with upstream and will make future development work much easier.
It is going to need some very thorough dev review/testing to make sure I haven't missed anything when merging in the upstream changes.